Run the CI Checks job at turbo concurrency 4 - #2305
Merged
Merged
Conversation
The job runs on a 4-vCPU runner; TypeScript 7 and esbuild are multi-threaded, so turbo's default of ten concurrent tasks only adds contention. Pinned to 4 CPUs, two rounds each: 96 s / 110 s at the default vs 90 s / 58 s at four. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong
The CI "Checks" job (
turbo run build typecheck lint) runs on a 4-vCPU runner with turbo's default concurrency of ten. TypeScript 7 and esbuild are multi-threaded, so ten concurrent tasks only fight for the four cores.What changed
The job passes
--concurrency=4.How you verified
Emulated with
taskset -c 0-3 turbo run build typecheck lint --force, two rounds each: 96 s and 110 s at the default vs 90 s and 58 s at four. Typecheck alone: 70 s at eight, 63 s at four, 61 s at two. Run-to-run noise is ±15 s, so treat this as a modest, consistent win rather than a precise figure.No linked issue.